Skip to content

Update PraisonAI version to 2.2.30 across Dockerfiles and related files#611

Merged
MervinPraison merged 1 commit intomainfrom
develop
Jun 5, 2025
Merged

Update PraisonAI version to 2.2.30 across Dockerfiles and related files#611
MervinPraison merged 1 commit intomainfrom
develop

Conversation

@MervinPraison
Copy link
Copy Markdown
Owner

@MervinPraison MervinPraison commented Jun 5, 2025

User description

  • Incremented the version of PraisonAI from 2.2.29 to 2.2.30 in Dockerfiles (Dockerfile, Dockerfile.chat, Dockerfile.dev, Dockerfile.ui).
  • Updated the version in the README.md and pyproject.toml files to reflect the new version.
  • Adjusted the deploy.py script to install the updated version of PraisonAI.
  • Ensured consistency across all relevant files for seamless integration.

PR Type

enhancement


Description

  • Bump PraisonAI version to 2.2.30 in all Dockerfiles and scripts

  • Update Homebrew formula to use v2.2.30 tarball

  • Update documentation and README to reflect new version

  • Bump PraisonAI Agents dependency to >=0.0.102 in pyproject.toml files

  • Increment PraisonAI Agents package version to 0.0.102


Changes walkthrough 📝

Relevant files
Enhancement
8 files
Dockerfile
Update PraisonAI version to 2.2.30 in base Dockerfile       
+1/-1     
Dockerfile.chat
Update PraisonAI version to 2.2.30 in chat Dockerfile       
+1/-1     
Dockerfile.dev
Update PraisonAI version to 2.2.30 in dev Dockerfile         
+1/-1     
Dockerfile.ui
Update PraisonAI version to 2.2.30 in UI Dockerfile           
+1/-1     
pyproject.toml
Bump PraisonAI and Agents versions in pyproject.toml         
+4/-4     
pyproject.toml
Bump PraisonAI Agents version to 0.0.102                                 
+1/-1     
deploy.py
Update Dockerfile generation to install PraisonAI 2.2.30 
+1/-1     
praisonai.rb
Update Homebrew formula to PraisonAI v2.2.30 tarball         
+2/-2     
Documentation
1 files
README.md
Document PraisonAI version 2.2.30 in Docker README             
+2/-2     

Need help?
  • Type /help how to ... in the comments thread for any questions about Qodo Merge usage.
  • Check out the documentation for more information.
  • Summary by CodeRabbit

    • Chores
      • Updated the minimum required version of the PraisonAI package to 2.2.30 across Dockerfiles and documentation.
      • Incremented the PraisonAI and PraisonAI Agents package versions to ensure compatibility.
      • Updated dependency references and metadata to reflect new package versions.

    - Incremented the version of PraisonAI from 2.2.29 to 2.2.30 in Dockerfiles (Dockerfile, Dockerfile.chat, Dockerfile.dev, Dockerfile.ui).
    - Updated the version in the README.md and pyproject.toml files to reflect the new version.
    - Adjusted the deploy.py script to install the updated version of PraisonAI.
    - Ensured consistency across all relevant files for seamless integration.
    @MervinPraison MervinPraison merged commit 1ff46bc into main Jun 5, 2025
    4 of 13 checks passed
    @coderabbitai
    Copy link
    Copy Markdown
    Contributor

    coderabbitai bot commented Jun 5, 2025

    Caution

    Review failed

    The pull request is closed.

    Walkthrough

    This update increments the minimum required version of the praisonai Python package from 2.2.29 to 2.2.30 across all Dockerfiles, deployment scripts, documentation, and project metadata. The praisonaiagents dependency is also updated from 0.0.101 to 0.0.102. No other functional or structural changes are included.

    Changes

    File(s) Change Summary
    docker/Dockerfile, docker/Dockerfile.chat, docker/Dockerfile.dev, docker/Dockerfile.ui Updated praisonai package version from 2.2.29 to 2.2.30 in pip install commands
    docker/README.md Updated PraisonAI package version references from 2.2.29 to 2.2.30 in documentation
    src/praisonai/pyproject.toml Bumped PraisonAI version to 2.2.30; updated praisonaiagents dependency to >=0.0.102
    src/praisonai-agents/pyproject.toml Bumped PraisonAI Agents version from 0.0.101 to 0.0.102
    src/praisonai/praisonai.rb Updated Homebrew formula to use PraisonAI 2.2.30 tarball and checksum
    src/praisonai/praisonai/deploy.py Updated Dockerfile creation to pin praisonai version 2.2.30

    Sequence Diagram(s)

    sequenceDiagram
        participant User
        participant Dockerfile/Deploy Scripts
        participant PyPI
    
        User->>Dockerfile/Deploy Scripts: Build/Deploy
        Dockerfile/Deploy Scripts->>PyPI: pip install praisonai==2.2.30
        PyPI-->>Dockerfile/Deploy Scripts: praisonai 2.2.30 package
        Dockerfile/Deploy Scripts-->>User: Ready with updated PraisonAI
    
    Loading

    Possibly related PRs

    • #595: Updates PraisonAI and related dependencies in Dockerfiles and metadata for a previous version bump.
    • #601: Performs a similar version bump of praisonai in Dockerfiles and configuration files, but for an earlier version step.
    • #609: Bumps PraisonAI from 2.2.28 to 2.2.29 in the same set of files, continuing the version update pattern.

    Poem

    A hop and a skip, a version anew,
    PraisonAI grows, as all good things do.
    From Docker to docs, the numbers align—
    2.2.30, oh how you shine!
    Agents and scripts, all up to date,
    This bunny approves, the upgrade is great!
    🐇✨


    📜 Recent review details

    Configuration used: CodeRabbit UI
    Review profile: CHILL
    Plan: Pro

    📥 Commits

    Reviewing files that changed from the base of the PR and between 370cc3e and e252475.

    ⛔ Files ignored due to path filters (2)
    • src/praisonai-agents/uv.lock is excluded by !**/*.lock
    • src/praisonai/uv.lock is excluded by !**/*.lock
    📒 Files selected for processing (9)
    • docker/Dockerfile (1 hunks)
    • docker/Dockerfile.chat (1 hunks)
    • docker/Dockerfile.dev (1 hunks)
    • docker/Dockerfile.ui (1 hunks)
    • docker/README.md (2 hunks)
    • src/praisonai-agents/pyproject.toml (1 hunks)
    • src/praisonai/praisonai.rb (1 hunks)
    • src/praisonai/praisonai/deploy.py (1 hunks)
    • src/praisonai/pyproject.toml (4 hunks)
    ✨ Finishing Touches
    • 📝 Generate Docstrings

    Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

    ❤️ Share
    🪧 Tips

    Chat

    There are 3 ways to chat with CodeRabbit:

    • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
      • I pushed a fix in commit <commit_id>, please review it.
      • Explain this complex logic.
      • Open a follow-up GitHub issue for this discussion.
    • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
      • @coderabbitai explain this code block.
      • @coderabbitai modularize this function.
    • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
      • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
      • @coderabbitai read src/utils.ts and explain its main purpose.
      • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
      • @coderabbitai help me debug CodeRabbit configuration file.

    Support

    Need help? Create a ticket on our support page for assistance with any issues or questions.

    Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

    CodeRabbit Commands (Invoked using PR comments)

    • @coderabbitai pause to pause the reviews on a PR.
    • @coderabbitai resume to resume the paused reviews.
    • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
    • @coderabbitai full review to do a full review from scratch and review all the files again.
    • @coderabbitai summary to regenerate the summary of the PR.
    • @coderabbitai generate docstrings to generate docstrings for this PR.
    • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
    • @coderabbitai resolve resolve all the CodeRabbit review comments.
    • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
    • @coderabbitai help to get help.

    Other keywords and placeholders

    • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
    • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
    • Add @coderabbitai anywhere in the PR title to generate the title automatically.

    CodeRabbit Configuration File (.coderabbit.yaml)

    • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
    • Please see the configuration documentation for more information.
    • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

    Documentation and Community

    • Visit our Documentation for detailed information on how to use CodeRabbit.
    • Join our Discord Community to get help, request features, and share feedback.
    • Follow us on X/Twitter for updates and announcements.

    Copy link
    Copy Markdown
    Contributor

    @gemini-code-assist gemini-code-assist bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Hello @MervinPraison, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

    Summary of Changes

    Hello team, gemini-code-assist here to provide a summary of this pull request. This PR, authored by MervinPraison, focuses on updating the project to use the latest versions of the core PraisonAI and praisonaiagents packages. The changes involve bumping the version numbers across various configuration files, Dockerfiles, documentation, and the deployment script to ensure consistency and leverage the features or fixes in the new releases (PraisonAI v2.2.30 and praisonaiagents v0.0.102).

    Highlights

    • PraisonAI Version Update: The core PraisonAI package dependency and references have been updated from version 2.2.29 to 2.2.30.
    • PraisonAI Agents Version Update: The praisonaiagents package dependency and references have been updated from version 0.0.101 to 0.0.102.
    • Docker Configuration Updates: All relevant Dockerfiles (Dockerfile, Dockerfile.chat, Dockerfile.dev, Dockerfile.ui) have been updated to install the new PraisonAI version.
    • Documentation and Deployment Updates: The README.md documentation and the deploy.py script have been updated to reflect the new PraisonAI version.
    • Dependency Lock File Updates: The uv.lock files for both praisonai and praisonaiagents have been updated to reflect the new package versions and their corresponding distribution hashes.
    • Homebrew Formula Update: The Homebrew formula (praisonai.rb) has been updated to point to the new PraisonAI release tag and includes the updated SHA256 hash.

    Changelog

    Click here to see the changelog
    • docker/Dockerfile
      • Updated praisonai dependency from >=2.2.29 to >=2.2.30.
    • docker/Dockerfile.chat
      • Updated praisonai dependency from >=2.2.29 to >=2.2.30.
    • docker/Dockerfile.dev
      • Updated praisonai dependency from >=2.2.29 to >=2.2.30.
    • docker/Dockerfile.ui
      • Updated praisonai dependency from >=2.2.29 to >=2.2.30.
    • docker/README.md
      • Updated listed PraisonAI version from >=2.2.29 to >=2.2.30.
      • Updated version pinning example from ==2.2.29 to ==2.2.30.
    • src/praisonai-agents/pyproject.toml
      • Updated praisonaiagents version from 0.0.101 to 0.0.102.
    • src/praisonai-agents/uv.lock
      • Updated praisonaiagents version from 0.0.101 to 0.0.102.
      • Updated sdist and wheel URLs and hashes for praisonaiagents.
    • src/praisonai/praisonai.rb
      • Updated Homebrew formula URL to v2.2.30 tag.
      • Updated SHA256 hash for the v2.2.30 tarball.
    • src/praisonai/praisonai/deploy.py
      • Updated hardcoded praisonai version in generated Dockerfile from ==2.2.29 to ==2.2.30.
    • src/praisonai/pyproject.toml
      • Updated PraisonAI project version from 2.2.29 to 2.2.30.
      • Updated praisonaiagents dependency from >=0.0.101 to >=0.0.102.
      • Updated PraisonAI poetry version from 2.2.29 to 2.2.30.
    • src/praisonai/uv.lock
      • Updated praisonai version from 2.2.29 to 2.2.30.
      • Updated praisonaiagents dependency from >=0.0.101 to >=0.0.102.
      • Updated sdist and wheel URLs and hashes for praisonaiagents.
    Using Gemini Code Assist

    The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

    Invoking Gemini

    You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

    Feature Command Description
    Code Review /gemini review Performs a code review for the current pull request in its current state.
    Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
    Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
    Help /gemini help Displays a list of available commands.

    Customization

    To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

    Limitations & Feedback

    Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

    You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


    Versions change and grow,
    Dockerfiles must follow,
    New code flows.

    Footnotes

    1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

    @qodo-code-review
    Copy link
    Copy Markdown

    PR Reviewer Guide 🔍

    Here are some key observations to aid the review process:

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ Recommended focus areas for review

    Dynamic SHA256 Calculation

    The SHA256 hash is being dynamically calculated using a shell command during build time. This approach may lead to inconsistent builds or failures if the GitHub repository is unavailable during build time.

    url "https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.30.tar.gz"
    sha256 `curl -sL https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.30.tar.gz | shasum -a 256`.split.first

    @qodo-code-review
    Copy link
    Copy Markdown

    PR Code Suggestions ✨

    Explore these optional code suggestions:

    CategorySuggestion                                                                                                                                    Impact
    Security
    Use pre-computed hash value

    The SHA256 calculation is being executed at runtime using backticks, which is
    insecure and unreliable for package management. Replace this with a pre-computed
    SHA256 hash value to ensure package integrity and avoid potential security
    issues.

    src/praisonai/praisonai.rb [6-7]

     url "https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.30.tar.gz"
    -sha256 `curl -sL https://github.com/MervinPraison/PraisonAI/archive/refs/tags/v2.2.30.tar.gz | shasum -a 256`.split.first
    +sha256 "a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6" # Replace with actual pre-computed SHA256 hash
    • Apply / Chat
    Suggestion importance[1-10]: 8

    __

    Why: This addresses a significant security and reliability issue where runtime shell command execution in package management is unsafe and unreliable. Using pre-computed SHA256 hashes is the standard secure practice for package integrity verification.

    Medium
    • More

    Copy link
    Copy Markdown
    Contributor

    @gemini-code-assist gemini-code-assist bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    Code Review

    This pull request effectively updates the PraisonAI version to 2.2.30 and PraisonAI Agents to 0.0.102 across various Dockerfiles, configuration files, and scripts. The changes are largely consistent and correctly reflect the new versions. The updates to pyproject.toml, uv.lock files, Dockerfiles, and the Homebrew formula are well-executed.

    I've identified a couple of areas in the docker/README.md where the PraisonAI Agents version needs to be updated to maintain consistency with the rest of the changes. Addressing these will ensure the documentation accurately reflects the new package versions.

    Summary of Findings

    • Documentation Inconsistency for PraisonAI Agents Version: The docker/README.md file lists an outdated version for PraisonAI Agents (0.0.92). This should be updated to 0.0.102 to align with the changes made in pyproject.toml files and the uv.lock files, as well as the intent described in the pull request.

    Merge Readiness

    The pull request is well-structured and addresses the version bump for PraisonAI and PraisonAI Agents comprehensively across most files. However, there are a couple of inconsistencies in docker/README.md regarding the PraisonAI Agents version that should be addressed to ensure documentation accuracy.

    I recommend making these minor corrections to the README before merging. As I am an AI, I am not authorized to approve pull requests; please ensure further review and approval by authorized team members.

    All Docker images use consistent, up-to-date versions:
    - PraisonAI: `>=2.2.29`
    - PraisonAI: `>=2.2.30`
    - PraisonAI Agents: `>=0.0.92`
    Copy link
    Copy Markdown
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    medium

    The PraisonAI Agents version listed here appears to be outdated. The pull request description and changes in pyproject.toml files indicate that PraisonAI Agents has been updated to version 0.0.102 (or >=0.0.102).

    Could you please update this line to reflect the correct version for PraisonAI Agents to ensure consistency with the actual dependencies?

    Suggested change
    - PraisonAI Agents: `>=0.0.92`
    - PraisonAI Agents: >=0.0.102

    To use specific versions, update the Dockerfile:
    ```dockerfile
    RUN pip install "praisonai==2.2.29" "praisonaiagents==0.0.92"
    RUN pip install "praisonai==2.2.30" "praisonaiagents==0.0.92"
    Copy link
    Copy Markdown
    Contributor

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    medium

    The example pip install command for version pinning uses praisonaiagents==0.0.92. Given that PraisonAI Agents has been updated to version 0.0.102 in this PR (as seen in pyproject.toml and the PR description), this example should also reflect the new version.

    Using an outdated version in the example might lead to confusion or users unintentionally installing an older, potentially incompatible version of praisonaiagents alongside praisonai==2.2.30.

    Would it be possible to update the agent version in this example command?

    Suggested change
    RUN pip install "praisonai==2.2.30" "praisonaiagents==0.0.92"
    RUN pip install "praisonai==2.2.30" "praisonaiagents==0.0.102"

    Copy link
    Copy Markdown

    @cursor cursor bot left a comment

    Choose a reason for hiding this comment

    The reason will be displayed to describe this comment to others. Learn more.

    ✅ BugBot reviewed your changes and found no bugs!


    BugBot free trial expires on June 9, 2025
    You have used $0.00 of your $50.00 spend limit so far. Manage your spend limit in the Cursor dashboard.

    Was this report helpful? Give feedback by reacting with 👍 or 👎

    @coderabbitai coderabbitai bot mentioned this pull request Jun 7, 2025
    shaneholloman pushed a commit to shaneholloman/praisonai that referenced this pull request Feb 4, 2026
    Update PraisonAI version to 2.2.30 across Dockerfiles and related files
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Projects

    None yet

    Development

    Successfully merging this pull request may close these issues.

    1 participant